Apparatus, method, and computer program product for solution provisioning

ABSTRACT

In one embodiment, a method for solution provisioning includes establishing a provisioning task, and obtaining a provisioning image for the provisioning task from a hardware memory. A provisioning implementer is configured based on the obtained provisioning image. The provisioning image comprises configuration information used for executing installation, scripts for executing installation, and information for mapping the configuration information to the scripts. In another embodiment, an apparatus for solution provisioning includes a hardware processor, and a task manager running on the hardware processor. The task manager is configured to establish a provisioning task and obtain a provisioning image for the provisioning task. The task manager configures a provisioning implementer based on the provisioning image obtained. The provisioning image comprises configuration information used for executing installation, scripts for executing installation, and information for mapping the configuration information to the scripts.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/065,916, filed Mar. 31, 2011, which claims priority to Chinese PatentApplication No. 201010139125.4 filed on Mar. 31, 2010, and which areherein incorporated by reference.

BRIEF SUMMARY

In one embodiment, a method for solution provisioning includesestablishing a provisioning task, and obtaining a provisioning image forthe provisioning task from a hardware memory. A provisioning implementeris configured based on the obtained provisioning image. The provisioningimage comprises configuration information used for executinginstallation, scripts for executing installation, and information formapping the configuration information to the scripts.

In another embodiment, an apparatus for solution provisioning includes ahardware processor, and a task manager running on the hardwareprocessor. The task manager is configured to establish a provisioningtask and obtain a provisioning image for the provisioning task. The taskmanager configures a provisioning implementer based on the provisioningimage obtained. The provisioning image comprises configurationinformation used for executing installation, scripts for executinginstallation, and information for mapping the configuration informationto the scripts.

In yet another embodiment, a computer program product for solutionprovisioning includes a computer readable storage medium having programinstructions embodied therewith, the program instructions executable bya processor to cause the processor to perform the foregoing method.

Other aspects and embodiments of the present invention will becomeapparent from the following detailed description, which, when taken inconjunction with the drawings, illustrate by way of example theprinciples of the invention.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 depicts a cloud computing node, according to one embodiment.

FIG. 2 depicts a cloud computing environment, according to oneembodiment.

FIG. 3 depicts abstraction model layers, according to one embodiment.

FIG. 4 shows a schematic block diagram of a system for solutionprovisioning in a cloud computing environment, according to oneembodiment.

FIG. 5 shows a schematic diagram of an open virtualization format (OVF)package according to the OVF standard, in one embodiment.

FIG. 6 shows a schematic block diagram of a method for solutionprovisioning in a cloud computing environment, according to oneembodiment.

DETAILED DESCRIPTION

The following description is made for the purpose of illustrating thegeneral principles of the present invention and is not meant to limitthe inventive concepts claimed herein. Further, particular featuresdescribed herein can be used in combination with other describedfeatures in each of the various possible combinations and permutations.

Unless otherwise specifically defined herein, all terms are to be giventheir broadest possible interpretation including meanings implied fromthe specification as well as meanings understood by those skilled in theart and/or as defined in dictionaries, treatises, etc.

It must also be noted that, as used in the specification and theappended claims, the singular forms “a,” “an” and “the” include pluralreferents unless otherwise specified. It will be further understood thatthe terms “comprises” and/or “comprising,” when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

The following description discloses several embodiments of storagesystems which allow data providers to share non-confidential informationwithout marking confidential information on their enterprise systems.For example, in one non-limiting embodiment, multiple entities can sharelists of data identifiers of files on their enterprise systems,duplicate data identifiers can be identified (which indicates that thefiles associated with the data identifiers are non-confidential sincethey appear on multiple entities' enterprise systems), and those fileshaving duplicate data identifiers may be stored in the storage networkwithout exposing any confidential data from any of the entities'enterprise systems.

Solution provisioning, as used herein, refers to procuring and preparingany systems, devices, connections, software, hardware, etc., to be usedthat enables a user or group of users to perform desired tasks, such asthrough server provisioning (including preparing one or more serverswith appropriate systems, data, software, etc., and making the one ormore servers available for network operations), user provisioning(including creating, maintaining, deactivating, modifying, etc., userobjects, user attributes, user accounts, etc., as they exist in one ormore systems, directories, or applications, possibly in response to arequest, system action, etc.), network provisioning (including preparingand activating mobile networks, internet resources, intranet resources,LAN resources, etc., along with mobile devices, network devices,routers, switches, etc., enabling connections from devices to thenetworks, etc.), etc., as would be understood by one of skill in the artupon reading the present descriptions.

A provisioning task, as used herein, refers to any action taken in orderto provide a user or group of users with the ability to perform one ormore desired tasks, such as through procurement of resources,preparation of systems, devices, connections, etc., initialization ofresources, deactivation of resources, etc., as would be understood byone of skill in the art upon reading the present descriptions.

A provisioning image, as used herein, refers to a collection ofinformation that is provided to one or more servers such that a user orgroup of users is capable of accessing and utilizing a solution. Theprovisioning image may include configuration information used forexecuting installation, scripts of any type (e.g., commands and/orexecutable code) for executing installation, and/or information formapping the configuration information to the scripts, and may relate toan image or virtual machine of any software, device, system, server,operating system (OS), etc. In a cloud computing environment, physicalsoftware products such as OS, middleware, software package, virtualmachines, virtual servers, etc., may be included in information of aprovisioning image.

A provisioning implementer, as used herein, refers to a module that iscapable of performing provisioning tasks, as described herein, as wellas procuring resources and utilizing a provisioning image to formulateone or more aspects of a provisioning solution to a user or group ofusers, such as on a server, virtual server, virtual machine, etc. Whenthe provisioning implementer is used, it may be launched by any system,device, routine, application, etc., such that it performs itsresponsibilities according to its designated functionality.

In one general embodiment, an apparatus for solution provisioningincludes a task manager configured to, in response to a receivedsolution provisioning request, establish a provisioning task and obtaina provisioning image for the provisioning task, and a provisioningimplementer configured to execute and monitor the provisioning taskestablished by the task manager, wherein the task manager configures andlaunches the provisioning implementer based on the provisioning imageobtained, and wherein the provisioning image comprises configurationinformation used for executing installation, scripts for executinginstallation, and information for mapping the configuration informationto the scripts.

In another general embodiment, a method for solution provisioningincludes establishing a provisioning task in response to a receivedsolution provisioning request, obtaining a provisioning image for theprovisioning task, configuring and launching a provisioning implementerbased on the obtained provisioning image, and executing and monitoringthe provisioning task using the provisioning implementer, wherein theprovisioning image comprises configuration information used forexecuting installation, scripts for executing installation, andinformation for mapping the configuration information to the scripts.

In yet another general embodiment, a computer program product forsolution provisioning includes a computer readable storage medium havingcomputer readable program code embodied therewith, the computer readableprogram code including computer readable program code configured to:establish a provisioning task in response to a received solutionprovisioning request, obtain a provisioning image for the provisioningtask, configure and launch a provisioning implementer based on theobtained provisioning image, and execute and monitor the provisioningtask using the provisioning implementer, wherein the provisioning imagecomprises configuration information used for executing installation,scripts for executing installation, and information for mapping theconfiguration information to the scripts.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based email). Theconsumer does not manage or control the underlying cloud infrastructureincluding network, servers, operating systems, storage, or evenindividual application capabilities, with the possible exception oflimited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forloadbalancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, handheld or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system/server 12 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20. As depicted, network adapter 20communicates with the other components of computer system/server 12 viabus 18. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 2 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 2) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 3 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes, in oneexample IBM® zSeries® systems; RISC (Reduced Instruction Set Computer)architecture based servers, in one example IBM pSeries® systems; IBMxSeries® systems; IBM BladeCenter® systems; storage devices; networksand networking components. Examples of software components includenetwork application server software, in one example IBM WebSphere®application server software; and database software, in one example IBMDB2C® database software. (IBM, zSeries, pSeries, xSeries, BladeCenter,WebSphere, and DB2 are trademarks of International Business MachinesCorporation registered in many jurisdictions worldwide).

Virtualization layer 62 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and Pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal provides access to the cloud computing environment forconsumers and system administrators. Service level management providescloud computing resource allocation and management such that requiredservice levels are met. Service Level Agreement (SLA) planning andfulfillment provide pre-arrangement for, and procurement of, cloudcomputing resources for which a future requirement is anticipated inaccordance with an SLA.

Workloads layer 66 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; transactionprocessing; solution provisioning; etc.

The following problems have typically existed in provisioning methods inthe prior art: (1) Diversity of software products: there are numeroustypes of software products in a cloud environment, both physicalsoftware products and virtual software products; however, the physicalsoftware products and virtual software products are very different inconfiguration and installation requirements, among other things; (2)High provisioning operation cost: different software is installed withproduct specific approaches, such that the personnel who cansuccessfully install one software may fail to install another software,more operation personnel, such as administrative staff, is required tohandle the provisioning tasks considering the number of softwareproducts, and it takes more time to configure and execute theprovisioning tasks considering the number of software products used; (3)High solution provisioning complexity: solution configurationcomplexity, the configuration information required by physical softwareproducts and virtual software products are very different, and theconfiguration information usually requires the user's manual input, nocommon process to drive the provisioning of solutions which may includeboth physical solution and virtual solutions, the provisioning processesrequired by physical software products and virtual software products arevery different from each other, and the installation of the solutionsrequires the installing personnel, such as the administrative staff, tobe familiar with the installation processes of virtual software productsas well as that of physical software products, while a common softwareinstalling technician usually cannot meet such requirements.

Accordingly, there is a need for a solution provisioning method whichallows the user to provision a solution conveniently and quickly, andwhich is transparent as to whether the solution is a physical solutionor a virtual solution, or a solution which combines a physical and avirtual solution.

The following exemplary embodiments help to further define and describesolution provisioning techniques and systems. It is to be understoodthat the invention is not limited to the exemplary embodimentsdisclosed. It should further be understood that not every feature of thepresently disclosed methods, apparatuses, computer program products, andsystems for solution provisioning are necessary to implement theinvention. It should further be understood that throughout thisdisclosure, where a process or method is shown or described, theoperations of the method may be performed in any order or concurrently,unless it is clear from the context that one operation depends onanother operation being performed previously.

As described above, the provisioning methods in the prior art fail toshield the differences in structures of physical and virtual solutionsfor users, and also fail to shield the differences in provisioningprocesses of physical and virtual solutions for users. Obviously, thereis a lack of a unified solution representation from the perspective ofprovisioning in the prior art: this is due, at least in part, tophysical solutions and virtual solutions being very different inconfiguration and provisioning manners from each other. Configurationdetails vary along with changes of OS, middleware, applications, etc.Further, the prior art lacks solution provisioning for criticalprocesses that allow for accelerating online updating of the solutionand reducing overall costs, and that allow a user to substantially notfeel the difference in provisioning processes of physical and virtualsolutions. Thereby, online updating of solutions in the prior art aredelayed, and it is hard to control the overall cost thereof.

According to one embodiment, a template image of a solution is provided,which includes configuration information of components included in thesolution and scripts for installation components, and associates/relatesboth of them with each other. Thus, a complex operation requiring theuser to configure each block is avoided.

According to another embodiment, a provisioning process is provided. Forusers, there is no difference whether the provisioning process is usedto provision a physical solution or a virtual solution. That is, theprovisioning process is consistent for physical solutions and virtualsolutions, thereby shielding the difference in provisioning of physicalsolution and virtual solutions for users.

Terms that are used in the descriptions and embodiments presented beloware specified here.

A “solution” as used herein refers to a set of machines, operatingsystems, middleware products, software packages, and/or virtualapplications used for realizing a specific user's business requirements.A “physical solution” as used herein usually comprises machines,operating systems, middleware products, and/or software packages asrequested. A “virtual solution” as used herein usually comprises virtualapplications, such as virtual machines. “Solution provisioning” as usedherein refers to a process of deploying an entire solution andactivating it in time, and that the provisioning process is suitable forprovisioning a physical solution as well as a virtual solution.

The following description is given in a cloud computing environment.However, it should be understood by those skilled in the art that thedescriptions and embodiments described herein are not limited to thisenvironment, and may be applied to any distributed network environment.

FIG. 4 shows a schematic block diagram of a hybrid solution provisioning(HSP) system 100 in a cloud computing environment according to oneembodiment.

As shown in FIG. 4, according to one embodiment, a solution provisioningsystem comprises a repository 140, a physical solution engine 150, avirtual solution engine 160, a target server 180, and a hybrid solutionprovisioning engine (e.g., HSP engine) 100 according to one embodiment.In a cloud computing environment, these components may be distributed ondifferent physical hosts, but may alternatively be distributed on thesame physical host.

As shown by the dashed box in FIG. 4, according to one embodiment of theinvention, a HSP engine 100 comprises a task manager 110, a parser 120,and a groups of provisioning implementers 130-1, . . . , 130-n(hereinafter commonly referred to as provisioning implementers 130,unless one or more provisioning implementers therein need to bedistinguished from each other specifically), where n is an positiveinteger. The number of provisioning implementers 130 may be equal to orless than that of solutions being provisioned by the HSP engine 100.

The HSP engine 100 is a component or system for realizing solutionprovisioning, according to one embodiment. The HSP engine 100 is used todrive different existing provisioning tools to perform actualinstallation and configuration work of a component based on the type ofeach component, and to coordinate the entire process of solutionprovisioning.

The HSP engine 100 may provision a plurality of solutions simultaneouslyresponsive to a plurality of provisioning requests 140, in one approach.HSP engine 100 coordinates and controls all the processes of solutionprovisioning. Moreover, HSP engine 100 further requests the provisioningimage from the repository 140.

The provisioning image is described in detail below. Each of theprovisioning images may be used for solution provisioning. Theprovisioning image comprises configuration information used forexecuting installation, scripts for executing installation, andinformation for mapping the configuration information to the scripts.Optionally, the provisioning image further comprises an installationmedium, thus in this case, the provisioning image comprises all theinformation used for realizing a solution provisioning.

As an example, a provisioning image may comprise a metadata portion thatmay be used as configuration information. The metadata portion mayinclude a physical configuration file, a syntax file, and a virtualconfiguration file. Each file is described in more detail below,according to one embodiment. The physical configuration file isdescribed first.

1. A physical configuration file: this is a file describing thestructure of a physical solution, including:

1.1 an element for describing the components of the physical solution,comprising a name and component attributes for specifying a machine orproduct, including component type, component serial number, etc., eachcomponent corresponding to a software product in the solution;

1.2 dependencies between the components; and

1.3 configuration information of the components, which is disclosed soas to be customized during the course of provisioning, e.g., forphysical software products, the configuration information corresponds tothe installation options.

An example of physical configuration file of a physical solution isshown below:

ITM.yaml     - Component : M1  //component name     Type : Machine  //component type     SN : 99FWP41  //serial number     - Component :SLES10SP2-32     Type : OS     Status : installed  //status     Host :M1   //host     DiskSize : 10M  //disk size     TargetDirectory :/vmfs/volumes/storage1/ // target directory     Password : passw0rd  //password     Install : Workflow:SPA.DeployOS  //relative path ofinstallation     program     Hypervisor : VMware-3.5     UserName :root   //user name     OSFamily : Linux   //operating system family    IP : 9.186.62.123   //IP address     CPUType : 32-bit   // CPU type    MemorySize : 1024   // memory size     CPUAmount : 2   // CPU amount    - Component: WasHV     Type : Middleware     Status : not-installed    Host : SLES10SP2-32     RootPassword : pw4test:     IPAddress :9.186.62.124     ConfiguredIPAddress : 9.186.62.132     Netmask :255.255.255.0     PrimaryDNS : 9.181.2.101     SecondDNS : 9.181.2.102    PowerOn : true     Gateway : 9.186.62.7     HostName : sam

The next file that is included in the metadata portion is a syntax file.

1. A syntax file: for mapping physical and virtual configurationinformation in a physical and virtual configuration file to scripts(e.g., commands and/or executable code), including:

1.1 The names of scripts, such as telnet, ping, etc.

1.2 Script options listed in a specified order (e.g., input parameters),for example, the input parameter of script ping, such as IP address9.186.62.132.

Moreover, the options in the syntax file may further be associated withthe parameters in physical/virtual configuration information files, soas to realize the customization of a certain component, in oneembodiment. Such an association is realized by inputting a parametername or attribute name, such as the attribute name ofConfigurelPAddress. For example, for the script ping, its inputparameter IP address may not be included in a syntax file, but is in acorresponding configuration file, and the script is associated with thecorresponding items in the configuration file (e.g., ConfigurelPAddress:9.186.62.132), thereby obtaining the IP address according to theassociation during provisioning.

A syntax file example is shown below:

ITM.syntax.yaml     WasHV :     //script name for middleware WasHV    //below are the options of script WasHV     HostName :ConfigNET.hostname //host name     Domain : ConfigNET.domain  //domainname     IPAddress : ConfigNET.ipaddr //IP address     Netmask :ConfigNET.netmask  //network mask     Gateway :ConfigNET.gateway //gateway name     PrimaryDNS : ConfigNET.pri_dns//primary DNS name     SecondDNS : ConfigNET.sec_dns //second DNS name    RootPassword : ConfigPWD_ROOT.password //root password    SLES10SP2-32 :  //script name for operating system SLES10SP2-     32    ......

Next, a virtual configuration file is described, according to oneembodiment.

1. Virtual configuration file: this is a file describing a structure ofa virtual solution, with content that is included in the virtualconfiguration file being similar to that in a physical configurationfile, including:

1.1 an element for describing the components of the virtual solution,comprising a name and component attributes for specifying a virtualmachine or virtual product, including component type, component ID,etc., each component corresponding to a software product in thesolution;

1.2 dependencies between the components; and

1.3 configuration information of the components, which is disclosed soas to be customized during the course of provisioning, e.g., for virtualsoftware products, the configuration information corresponds to theinstallation options.

The virtual configuration file is described with Open VirtualizationFormat (OVF) format, according to one embodiment. OVF is specific forthe case of provisioning a virtual solution, used for describing thevirtual solution, provisioning customization attributes and Hypervisorinformation (including address and certification information).

OVF is an open standard for packaging and distributing a virtual tool(or software) running on a virtual machine. The standard describes anopen, safe, transferrable, efficient and scalable format for packagingand distributing software to run on a virtual machine. OVF is brieflyintroduced in FIG. 5, according to one embodiment. FIG. 5 shows aschematic diagram of an OVF package according to the OVF standard.

The OVF standard defines three elements: OVF package, OVF descriptor andOVF environment file. OVF package is the core of OVF standard, OVFpackage is a distribution package, which comprises the followingcontent: (1) an OVF descriptor file (.ovf). This usually represents OVFenvelope and is mainly a subject supported by the tool. OVF descriptorfile defines the content and demands of a package virtual tool tosupport successful and consistent provisioning of the package. OVFdescriptor file adopts XML format. (2) 0 to 1 OVF manifest file (.mf).The manifest file comprises SHA-1 abstracts of all files in OVF package.The manifest is used to supply data integrity of the package. (3) 0 to 1OVF certification file (.cert). OVF package can be signed by signing themanifest file. The signature of the abstract is stored in a .cert filealong with a base64-encoded X.509 certificate. The certificate is usedto ensure the authenticity of the package. (4) 0 to a plurality of diskimage files. These files represent the virtual disk supporting thevirtual image or tool defined. Usually, the package comprises aworkpiece required by the tool, wherein a virtual disk, localizedlanguage resources and other workpieces are comprised.

The OVF envelope describes all virtual machine metadata (includingvirtual hardware) constituting the OVF package. The OVF envelopecomprises the following parts: (1) version indication defined by XMLname space URI; (2) a file reference list referring to all externalfiles, which is a part of OVF package defined by References elements andits File sub element. They are usually virtual disk files, ISO imagesand international resources; (3) tool level metadata defined by sectionelement for describing the content such as network and virtual disk,etc.; (4) a description of the tool content, which can be a singlevirtual machine (VirtualSystem element) or a series of virtual machines(VirtualSystemCollection element); (5) a message resources package normaimed from 0 to a plurality of regions, where each region is defined bythe corresponding element of strings. The OVF envelope is created andused in the stage of packaging and distributing a life period of avirtual tool.

The OVF environment is an XML file, which is generated by OVFprovisioning platform during the process of provisioning OVF package,and is provided to be used by visitor software in the virtual systemhaving been provisioned, according to one embodiment. The OVFenvironment file is used to provide the attribute variable informationof the visitor software (belonging to the OVF package having beenprovisioned) of a virtual system, for “customizing” the visitor virtualsystem. The creator (OVF envelope) of the OVF package descriptordesignates which custom attributes need variable input. In theprovisioning activities of an OVF package, a provisioning platform willcollect values associating with a self-defined attribute key, andconstruct the OVF environment file.

The OVF environment is used in the stage of provisioning a life periodof a virtual tool.

The provisioning image also comprises scripts for executinginstallation. Each script is an executable file for executinginstallation and activation of each component by utilizing configurationinformation, such as in the metadata. A script (e.g., command) may becalled to execute provisioning of a product. For a given product, aplurality of scripts may be used. Each script comprises a script pathand a script syntax, including a script parameter and a right serial.For example, path Install: Workflow: SPA.DeployOS is a relative path.

The provisioning image also includes installation media. Anyinstallation media files may be included, such as installation mediabinaries files, installation media wizard, installation media package,product script, virtual application, etc., such as TPM workflows.

According to one embodiment, the provisioning image may help theprovisioning engine learn the inner dependencies of the solutions, andunderstand the structures of the solutions, such as the files packagedin the solutions, for what the files are used and how to use the files;and describing the syntax of the provisioning script packaged in thesolutions, such as valid parameter name/value and parameter pairs, suchthat configuration can be performed automatically in the process ofprovisioning, without any input of the configuration informationmanually by the users. The provisioning image can be compressed into thefiles to distribute over a network, in one approach.

These provisioning images need not be integrated together with an HSPengine, but may be located on another server in the network.Furthermore, a provisioning image may be created by using the formatdescribed above and uploaded to a provisioning image repository, whichmay be used to store and share solution images for different services,in one approach. The provisioning image repository allows differenttechnicians in a software development team contribute their solutionimages. Since different users may need the same or similar services,reusing the provisioning image by reusing or simply modifying a portionof metadata is possible and highly efficient. The provisioning imagerepository may maintain and manage the provisioning images contributedby different users, thereby reducing the online time of the solutions,in one approach.

As shown in FIG. 4, as an example, the provisioning image is shown beingstored in the repository 140 on another physical host. The repository140 is used to store a plurality of provisioning images contributed bydifferent technicians according to an embodiment. HSP engine 100 and therepository 140 interact to obtain the provisioning image. In the exampleof FIG. 4, suppose the provisioning image comprises installation media,it comprises thereby all information required to realize a solutionprovisioning.

Task manager 110, responsive to the request of solution provisioningreceived, establishes the provisioning task, obtains the provisioningimage for the provisioning task, and configures and launchesprovisioning implementers 130 based on the provisioning image obtained.Provisioning implementers 130 are used for executing and monitoring theprovisioning task assigned to it by the task manager 110. The operationsof all the provisioning implementers is coordinated and controlled bythe task manager 110.

The task manager 110 calls for provisioning images having the same namefrom the repository 140 based on the solution names in the solutionprovisioning request. After obtaining the provisioning image, the taskmanager 110 launches a corresponding provisioning implementer 130, andtransmits the corresponding information in the provisioning image to theprovisioning implementer 130.

Preferably, before launching a provisioning implementer 130 to execute atask for a solution provisioning, the task manager 110 first checkswhether the solution is being provisioned or has been provisioned on thetarget server. The check is based on job control data maintained in HSPengine 100 and data comprised in the solution provisioning request, suchas the name of the solution.

The embodiment proposes “job control data” for synchronizing andavoiding repeated provisioning of the same solution on the same server.By default, the job control data comprises the solution name, thetransfer (its value can be completed or uncompleted) from aninstallation media to the target server. Optionally, the job controldata further comprises the unpacking (its value can be started orcompleted) of a provisioning image on the target server and execution(its value can be waiting, executing or completed) of a script. Anexemplary example of the job control data is shown below:

SolutionName : ITM   //solution name being ITM     -Transfer: completed//transfer of installation media having       //completed     -Unpack:Started  //unpacking being started, optional     -Script:Waiting  //script being waiting for execution,    // and its value canbe a default value,    //optional

If it is determined that the same solution is being or has beenprovisioned on the target server, then the task manager 110 discards thesolution provisioning request and/or returns a prompt message, such as“the same solution is being or has been provisioned,” thereby avoidingthe conflict caused by repeated provisioning of a same solution on thesame target server. Certainly, the task manager 110 may also not respondto the solution provisioning request, in place of sending the promptmessage.

After it is determined that there is not a same solution being or havingbeen provisioned on the target server, the task manager 110 creates thejob control data for the solution. Except for that item of the solutionname in the job control data being filled with the name carried in theprovisioning request, all other items have a default value or are null.

After having created the job control data, task manager 110 calls forthe provisioning image having the same name from repository 140 based onthe solution name, and then launches corresponding provisioningimplementer 130, and transfers the job control data created for theprovisioning task to the provisioning implementer 130 launched.

After having been launched, provisioning implementer 130 instructs therepository 140 to transfer the corresponding provisioning image to atarget server 180. After being transferred successfully, the system willreturn a message of transfer success to the provisioning implementer130, and transfer back corresponding information, such as a file path.After receiving a success instruction, the provisioning implementer 130modifies the value of the item transfer in the job control data to becompleted. If the provisioning implementer 130 still does not receivethe message of transfer success after a predefined time period aftersending an instruction, the provisioning implementer 130 may default atransfer failure, and may instruct again the repository 140 to transfermodule image to the target server 180.

In the case of the module image not including installation media, afterbeing launched, the provisioning implementer 130 may instruct otherparties having installation media to transfer the installation media tothe target server.

The provisioning implementer 130 may begin to execute a script bydefault after a predetermined time (e.g., 1 minute, 10 minutes, 20minutes, or longer or shorter) after receiving the message of transfersuccess.

Alternatively, in the case where the job control data comprises theitems Unpack and Script, the provisioning implementer 130 furtherrecords their values as described below, in one approach. Aftertransferring successfully, the module image is unpacked automatically onthe target server 180. If automatic unpacking succeeds, the system willreturn the message of automatic unpacking success to the provisioningimplementer 130. After receiving success instruction, the provisioningimplementer 130 modifies the value of the item Unpack in the job controldata to be started.

After being unpacked successfully, the system will return the message ofunpack completion to the provisioning implementer 130, and meanwhilereturn corresponding information, such as a folder path including theunpack files. After receiving the success instruction, the provisioningimplementer 130 modifies the value of the item Unpack in the job controldata to be completed, in one approach.

If the provisioning implementer 130 still does not receive a message ofunpack success after a predefined time period from the beginning ofreceiving a message of automatic unpacking success, the provisioningimplementer 130 may default an unpack failure, and may again instructthe repository 140 to transfer module image to the target server 180,repeating the above process, in one approach.

Alternatively, after receiving an instruction from the provisioningimplementer 130, repository 140 unpacks corresponding module image tomerely obtain the installation media therein, and then compresses theinstallation media to a compressed file, such as ITM.zip file, andtransfers the compressed file to target server 180, in one approach.

After receiving the required provisioning image from the repository 140,task manager 110 transfers the provisioning image to parser 120.Certainly, the parser 120 may also be integrated with the task manager110 into one unit, in one approach.

Parser 120 is used to unpack the provisioning image, and merely obtainsthe metadata and script therein. It shall be noted that the repository140 can unpack the corresponding provisioning image after receiving theprovisioning image request from the task manager 110, obtain themetadata and script therein, and compress it into a compressed filehaving the same name as the module image (or another name), and thentransfer the compressed file to the task manager 110. Consequently, theparser 120 merely needs to execute unpacking. Then, the parser 120returns the information parsed to the task manager 110, in one approach.

Once receiving the metadata and script of parser 120, the task manager110 transfers the metadata and script to provisioning implementer 130launched for the provisioning task, in one approach.

Having received the metadata and script from the task manager 110, theprovisioning implementer 130 checks whether the value of the item“Unpack” in the job control data is “completed” or not. If it is not,provisioning implementer 130 may wait, and periodically check the valueof the item “Unpack.” Once the value of the item “Unpack changes to“completed,” the provisioning implementer 130 opens the syntax file inthe metadata, and executes script according to the script order listedin the syntax file, and transfers the options listed in the syntax fileto corresponding scripts simultaneously.

For a solution, there can be one or more scripts. The number and contentof the scripts is customized by the user on demand. The difference ofconfiguration information caused by the difference of demands isreflected in a physical/virtual configuration file. That is, the scriptis associated with the configuration information. While customizing ascript, the user writes the corresponding configuration information usedby the script in the physical/virtual configuration file. For example,for the installation of the component SLES10SP2-32, the disk sizerequired can vary by different machines. Therefore, the users canassociate the script SLES10SP2-32 with the disk size required, andchange the value of the item DiskSize whose component ID in the physicalconfiguration file is SLES10SP2-32 to be 10M.

With respect to each script, the provisioning implementer 130 determineswhether the configuration file is physical or virtual according to thetype of the component in the configuration file associated with thescript, and then executes corresponding script by calling physicalsolution engine 150 or virtual solution engine 160, and meanwhile theprovisioning implementer 130 sets the value of the item Script in thejob control data as Executing.

Physical solution engine 150 is an existing tool used for provisioningphysical solutions, and is called by HSP engine 100, such as Red Hat RPMPackage Manager, FreeBSD Ports System, Windows Installer as well asEnterprises JavaBeans (EJB), xCat, IBM Tivoli Rembo, IBM SolutionAssembly Toolkit (SAT), etc. Virtual solution engine 160 is an existingtool used for provisioning virtual solutions, and is called by HSPengine 100, such as XEN.

Having provisioned, physical solution engine 150 or virtual solutionengine 160 returns a provisioning completion indication to provisioningimplementer 130. Having received the provisioning completion indicationof the last script in the syntax file, provisioning implementer 130 setsthe value of the item Script in the job control data as “Completed.”Once the value of script is set to “Completed,” provisioning implementer130 returns the provisioning completion indication to the task manager110. After receiving the provisioning completion indication, taskmanager 110 releases corresponding provisioning implementer 130.

Task manager 110 and provisioning implementer 130 both need to maintaintheir own data according to one embodiment. For example, task manager110 may also maintain the status information of each task (e.g., whetheror not the task is running or succeed) as well as the resourceinformation associated with each task (e.g., the size of memoryrequired) and log information. Provisioning implementer 130 may alsomaintain the status information, resource information and loginformation and the like for each solution provisioning. The informationin HSP engine 100 may be stored in a database and may also be stored asa data file, as long as relevant information may be stored, in oneapproach.

If the solution provisioning has not been completed or succeeded,provisioning implementer 130 will set the value of the item Script inthe job control data to a specified value, such as “Error.” Then, duringthe provisioning of the solution next time, the task manager 110 furthermakes a check before provisioning. In this case, the job control datafor the solution has existed, but the value of the item Script thereinis Error; that is, the provisioning is not executing or uncompleted.Thus, task manager 110 finds out the existing metadata and script forthe solution according to the information maintained by it, and startsprovisioning implementer 130 to execute the script based on the metadataagain.

As known by those skilled in the art, the various components shown inFIG. 4, such as task manager, parser, and every provisioningimplementer, may be realized as one or more hardware units, such as anapplication-specific integrated circuit (ASIC), a digital signalprocessing (DSP) module, etc., and may further be realized as one ormore software units, such as separate programs, code blocks, modules,etc., or may be realized as a combination thereof. Its specificimplementation depends on the user's systems, structures, and desires.

FIG. 6 shows a schematic block diagram of a method 600 for solutionprovisioning in a cloud computing environment according to oneembodiment. The method 600 may be executed in any desired environment,including those described in FIGS. 1-5, in various embodiments.

In operation 602, it is determined whether or not a solutionprovisioning request is received. If yes, a provisioning task isestablished for the solution provisioning request, and the method 600proceeds to operation 604; otherwise, the method 600 returns tooperation 602.

In operation 604, a provisioning task is established for the solutionprovisioning request.

In operation 606, a provisioning image for the provisioning task isobtained. It may be obtained by requesting a corresponding provisioningimage from the repository based on the solution name in the solutionprovisioning request.

In operation 608, the provisioning implementer is configured andlaunched based on the provisioning image obtained. The configuration isrealized by parsing the provisioning image obtained and transferring theparsed provisioning image to the provisioning implementer.

In operation 610, the provisioning task is executed and monitored by theprovisioning implementer. As described above, the operation isprovisioning based on the information in the provisioning imageobtained. It is realized by using the configuration file in the metadatato execute the script according to the order prescribed by the syntaxfile in the metadata.

The method 600 described above is used when executing the solutionprovisioning for the first time. As described above, if the firstexecution is uncompleted or failed, when executing the solutionprovisioning subsequently, operation 606 may be omitted.

The embodiments described above may be realized in any appropriatemanner, including hardware, software, firmware, or any combinationsthereof. Or, the embodiments may at least be partially realized ascomputer software running on one or more data processor and/or digitalsignal processors. The elements and components of the embodiments may berealized physically, functionally, and logically in any appropriatemanner. Also, the function may be realized in one component, multiplecomponents, or as a part of other functional components. Thus, theembodiments may be realized in one single component, or may bephysically and functionally distributed between different components andprocessors.

In one embodiment, a computer program product for solution provisioningcomprises a computer readable storage medium having computer readableprogram code embodied therewith. The computer readable program codeincludes computer readable program code configured to establish aprovisioning task in response to a received solution provisioningrequest, computer readable program code configured to obtain aprovisioning image for the provisioning task, computer readable programcode configured to configure and launch a provisioning implementer basedon the obtained provisioning image, and computer readable program codeconfigured to execute and monitor the provisioning task using theprovisioning implementer. The provisioning image comprises configurationinformation used for executing installation, scripts for executinginstallation, and information for mapping the configuration informationto the scripts.

In another embodiment, the configuration information may comprise atleast one of the following: physical configuration informationdescribing a structure of a physical solution, and virtual configurationinformation describing a structure of a virtual solution.

According to another embodiment, the information for mapping theconfiguration information to the scripts may comprise script names andscript options listed according to a specified order.

In yet another embodiment, the computer program product may includecomputer readable program code configured to parse the provisioningimage to obtain the configuration information in the provisioning image,wherein the computer readable program code configured to configure theprovisioning implementer comprises computer readable program codeconfigured to transfer the configuration information obtained from theprovisioning image through parsing to the provisioning implementer.

In another embodiment, the computer program product may include computerreadable program code configured to determine that the solutionrequested is being or has been provisioned on a target server based onthe solution provisioning request before launching the provisioningimplementer, and computer readable program code configured to return aprompt message.

In yet another embodiment, the computer program product may includecomputer readable program code configured to determine that therequested solution is not being or has not been provisioned on thetarget server, and computer readable program code configured to createjob control data for synchronization with respect to the solutionprovisioning request to synchronize and avoid repeated provisioning of asame solution on a same sever. The job control data at least comprises asolution name and an item indicating a transfer from an installationmedia to the target server. In a further embodiment, the job controldata may comprise an item indicating decompression of a provisioningimage on the target server and an item indicating execution of scripts.

According to another embodiment, the computer program product mayinclude a plurality of provisioning implementers, wherein eachprovisioning implementer is configured to provision at least onesolution.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above-described exemplary embodiments, butshould be defined only in accordance with the following claims and theirequivalents.

What is claimed is:
 1. An apparatus for solution provisioning, theapparatus comprising: a hardware processor; a task manager running onthe hardware processor, the task manager being configured to establish aprovisioning task and obtain a provisioning image for the provisioningtask; and wherein the task manager configures a provisioning implementerbased on the provisioning image obtained, and wherein the provisioningimage comprises configuration information used for executinginstallation, scripts for executing installation, and information formapping the configuration information to the scripts.
 2. The apparatusaccording to claim 1, comprising a provisioning implementer configuredto execute and monitor the provisioning task established by the taskmanager.
 3. The apparatus according to claim 1, wherein theconfiguration information comprises at least one of the following:physical configuration information describing a structure of a physicalsolution and virtual configuration information describing a structure ofa virtual solution.
 4. The apparatus according to claim 1, wherein theinformation for mapping the configuration information to the scriptscomprises script names and script options listed according to aspecified order.
 5. The apparatus according to claim 1, comprising aparser configured to parse the provisioning image to obtain informationfrom the provisioning image, wherein the task manager configures theprovisioning implementer by transferring the configuration informationobtained from the provisioning image through parsing to the provisioningimplementer.
 6. The apparatus according to claim 1, wherein beforelaunching the provisioning implementer, the task manager determines thatthe solution requested is being or has been provisioned on a targetserver based on the solution provisioning request and returns a promptmessage.
 7. The apparatus according to claim 1, comprising a pluralityof provisioning implementers, wherein each provisioning implementer isconfigured to provision at least one solution.
 8. A system for solutionprovisioning, comprising: the apparatus according to claim 1; arepository for storing the provisioning image; and a target server onwhich the solution is provisioned.
 9. A method for solutionprovisioning, the method comprising: establishing a provisioning task;obtaining a provisioning image for the provisioning task from a hardwarememory; and configuring, using a hardware processor, a provisioningimplementer based on the obtained provisioning image, wherein theprovisioning image comprises configuration information used forexecuting installation, scripts for executing installation, andinformation for mapping the configuration information to the scripts.10. The method according to claim 9, comprising executing and monitoringthe provisioning task using the provisioning implementer.
 11. The methodaccording to claim 9, wherein the configuration information comprises atleast one of the following: physical configuration informationdescribing a structure of a physical solution, and virtual configurationinformation describing a structure of a virtual solution.
 12. The methodaccording to claim 9, wherein the information for mapping theconfiguration information to the scripts comprises script names andscript options listed according to a specified order.
 13. The methodaccording to claim 9, comprising parsing the provisioning image toobtain the configuration information in the provisioning image, whereinconfiguring the provisioning implementer comprises transferring theconfiguration information obtained from the provisioning image throughparsing to the provisioning implementer.
 14. The method according toclaim 9, comprising, before launching the provisioning implementer:determining that the solution requested is being or has been provisionedon a target server based on the solution provisioning request, andreturning a prompt message; and determining that the requested solutionis not being or has not been provisioned on the target server, andcreating job control data for synchronization with respect to thesolution provisioning request to synchronize and avoid repeatedprovisioning of a same solution on a same sever, wherein the job controldata at least comprises a solution name and an item indicating atransfer from an installation media to the target server, and whereinthe job control data comprises an item indicating decompression of aprovisioning image on the target server and an item indicating executionof scripts.
 15. The method according to claim 9, comprising a pluralityof provisioning implementers, wherein each provisioning implementer isconfigured to provision at least one solution.
 16. A computer programproduct for solution provisioning, the computer program productcomprising a computer readable storage medium having programinstructions embodied therewith, the program instructions executable bya processor to cause the processor to: establish, by the processor, aprovisioning task; obtain, by the processor, a provisioning image forthe provisioning task; and configure, by the processor, a provisioningimplementer based on the obtained provisioning image, wherein theprovisioning image comprises configuration information used forexecuting installation, scripts for executing installation, andinformation for mapping the configuration information to the scripts.17. The computer program product according to claim 16, wherein theconfiguration information comprises at least one of the following:physical configuration information describing a structure of a physicalsolution, and virtual configuration information describing a structureof a virtual solution, and wherein the information for mapping theconfiguration information to the scripts comprises script names andscript options listed according to a specified order.
 18. The computerprogram product according to claim 16, wherein the program instructionsare executable by a processor to cause the processor to parse theprovisioning image to obtain the configuration information in theprovisioning image, wherein configuring the provisioning implementercomprises includes transferring the configuration information obtainedfrom the provisioning image through parsing to the provisioningimplementer.
 19. The computer program product according to claim 16,wherein the program instructions are executable by a processor to causethe processor to: determine that the solution requested is being or hasbeen provisioned on a target server based on the solution provisioningrequest before launching the provisioning implementer and return aprompt message; and determine that the requested solution is not beingor has not been provisioned on the target server and create job controldata for synchronization with respect to the solution provisioningrequest to synchronize and avoid repeated provisioning of a samesolution on a same sever, wherein the job control data at leastcomprises a solution name and an item indicating a transfer from aninstallation media to the target server, wherein the job control datafurther comprises an item indicating decompression of a provisioningimage on the target server and an item indicating execution of scripts.20. The computer program product according to claim 16, wherein theprogram instructions are executable by a processor to cause theprocessor to execute and monitor the provisioning task using theprovisioning implementer.